You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2013/03/18 03:19:59 UTC

Git and check in messages

Hi,

Just noticed that the checkin messages are set up to do one message per (local) commit. Is this the behaviour we want? If you do a large number of small commits and then push you get a lot of emails sent to the list.

Thanks,
Justin

Re: Git and check in messages

Posted by Frédéric THOMAS <we...@hotmail.com>.
> What about those who are not using the command line but relying on Tower 
> or Git Tortoise? Is that still an option?

yep.

> Who was supposed to to that, I'm not sure, Carlos ?

-Fred

-----Message d'origine----- 
From: Justin Mclean
Sent: Monday, March 18, 2013 3:34 AM
To: dev@flex.apache.org
Subject: Re: Git and check in messages

Hi,

> Another possibility is to use interactive rebase where you squash 
> files/even lines of file inside a single commit you there you can even 
> change the commit orders, use git rebase -i HEAD~4 to interactily change 
> your commits.

This really need to be documented on the WIki people who are not familiar 
with GIt are going to get into trouble here.

What about those who are not using the command line but relying on Tower or 
Git Tortoise? Is that still an option?

Thanks,
Justin

Re: Git and check in messages

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> Another possibility is to use interactive rebase where you squash files/even lines of file inside a single commit you there you can even change the commit orders, use git rebase -i HEAD~4 to interactily change your commits.

This really need to be documented on the WIki people who are not familiar with GIt are going to get into trouble here.

What about those who are not using the command line but relying on Tower or Git Tortoise? Is that still an option?

Thanks,
Justin

Re: Git and check in messages

Posted by Frédéric THOMAS <we...@hotmail.com>.
> You are very likely to have unstaged changes if your built the SDK

That's why I committed a .gitignore file.

> However it's not possible to run (unlike git push)

Only do this on commits that haven’t been pushed an external repository.

-Fred

-----Message d'origine----- 
From: Justin Mclean
Sent: Monday, March 18, 2013 3:38 AM
To: dev@flex.apache.org
Subject: Re: Git and check in messages

Hi,

>  git rebase -i HEAD~4

However it's not possible to run (unlike git push) if you have uncommitted 
local changes, that makes it less than useful IMO. You are very likely to 
have unstaged changes if your built the SDK.

Justin

Re: Git and check in messages

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

>  git rebase -i HEAD~4

However it's not possible to run (unlike git push) if you have uncommitted local changes, that makes it less than useful IMO. You are very likely to have unstaged changes if your built the SDK.

Justin

Re: Git and check in messages

Posted by Frédéric THOMAS <we...@hotmail.com>.
use git rebase -i HEAD~4 to interactily change your 4 last commits

-----Message d'origine----- 
From: Frédéric THOMAS
Sent: Monday, March 18, 2013 3:30 AM
To: dev@flex.apache.org
Subject: Re: Git and check in messages

Sorry, I meant the usual behavior*

Another possibility is to use interactive rebase where you squash files/even
lines of file inside a single commit you there you can even change the
commit orders, use git rebase -i HEAD~4 to interactily change your commits.

-Fred

-----Message d'origine----- 
From: Frédéric THOMAS
Sent: Monday, March 18, 2013 3:24 AM
To: dev@flex.apache.org
Subject: Re: Git and check in messages

That's usage behavior but there is the possibility to amend your last commit
overriding the last message too using git commit --amend

-Fred

-----Message d'origine----- 
From: Justin Mclean
Sent: Monday, March 18, 2013 3:19 AM
To: dev@flex.apache.org
Subject: Git and check in messages

Hi,

Just noticed that the checkin messages are set up to do one message per
(local) commit. Is this the behaviour we want? If you do a large number of
small commits and then push you get a lot of emails sent to the list.

Thanks,
Justin

Re: Git and check in messages

Posted by Frédéric THOMAS <we...@hotmail.com>.
Sorry, I meant the usual behavior*

Another possibility is to use interactive rebase where you squash files/even 
lines of file inside a single commit you there you can even change the 
commit orders, use git rebase -i HEAD~4 to interactily change your commits.

-Fred

-----Message d'origine----- 
From: Frédéric THOMAS
Sent: Monday, March 18, 2013 3:24 AM
To: dev@flex.apache.org
Subject: Re: Git and check in messages

That's usage behavior but there is the possibility to amend your last commit
overriding the last message too using git commit --amend

-Fred

-----Message d'origine----- 
From: Justin Mclean
Sent: Monday, March 18, 2013 3:19 AM
To: dev@flex.apache.org
Subject: Git and check in messages

Hi,

Just noticed that the checkin messages are set up to do one message per
(local) commit. Is this the behaviour we want? If you do a large number of
small commits and then push you get a lot of emails sent to the list.

Thanks,
Justin

Re: Git and check in messages

Posted by Frédéric THOMAS <we...@hotmail.com>.
That's usage behavior but there is the possibility to amend your last commit 
overriding the last message too using git commit --amend

-Fred

-----Message d'origine----- 
From: Justin Mclean
Sent: Monday, March 18, 2013 3:19 AM
To: dev@flex.apache.org
Subject: Git and check in messages

Hi,

Just noticed that the checkin messages are set up to do one message per 
(local) commit. Is this the behaviour we want? If you do a large number of 
small commits and then push you get a lot of emails sent to the list.

Thanks,
Justin