And you loose all of your local commit history then. I'm not sure if that
is ideal or not - guess it depends on how big the change is but that local
history log may be useful.
Well, you'll still have the details in the logs, well, just found a good
reading about the different option [1] have a glance at it.
Still no idea how we indicate what changes have occurred in JIRA.
Previously we supplied a SVN revision number with would identify the
changes easily and you'll know if your code had that change or not.
You can check writing the JIRA ticket id in the commit message(s), push
it/them , then go to JIRA, in the source tab, you should see all the
modified files (if this feature is not broken again).
-Fred
[1] http://365git.tumblr.com/post/4364212086/git-merge-squash
-----Message d'origine-----
From: Justin Mclean
Sent: Monday, March 18, 2013 4:06 AM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
Hi,
which I squash a merge time using git merge --squash -m 'new ' newFeature.
And you loose all of your local commit history then. I'm not sure if that is
ideal or not - guess it depends on how big the change is but that local
history log may be useful.
Still no idea how we indicate what changes have occurred in JIRA. Previously
we supplied a SVN revision number with would identify the changes easily and
you'll know if your code had that change or not.
Thanks,
Justin
