Hervé,
I have not used this yet. However it seems mostly merging would be a
problem. Just annotating commits in the appropriate Jira/Ticket namespace
will probably run seldomly into this situation.
Normally I would put the ticket into the summary line as well.
Regards Mirko
--
Sent from my mobil
yes, that would do the job: great!
But the article explains lots of problems to effectively use this on a shared
repository: do you know if it's ok with actual git version (1.7.*) and Apache
setup?
(notice: I'm using git through my IDE which doesn't tell anything about notes)
Regards,
Hervé
L
Hello,
you could use git notes http://git-scm.com/2010/08/25/notes.html for this.
Regards Mirko
--
Sent from my mobile
On Dec 2, 2012 9:42 AM, "Kristian Rosenvold"
wrote:
> You can't. Once a commit has been pushed there's no change that can be
> done.
>
> In practice, if you want the 2-way ref
You can't. Once a commit has been pushed there's no change that can be done.
In practice, if you want the 2-way reference, you need to add the
jira-reference to the commit up-front with the classical [MNG-5379]
prefix in the message.
Kristia
2012/12/2 Hervé BOUTEMY :
> I created MNG-5397 Jira
I created MNG-5397 Jira issue for "Use SLF4J for logging", with a classical
comment to link to svn revision.
I just added a link to equivalent git commit, now we're using git.
One thing I used to do with svn in such a case is changing svn:log to add Jira
issue reference to the revision commit lo
