From: Antoine Pelisse <email@example.com> To: Ed Hutchins <firstname.lastname@example.org> Cc: Junio C Hamano <email@example.com>, git <firstname.lastname@example.org> Subject: Re: Feature request: "author branch" in commit object Date: Wed, 3 Jul 2013 18:16:41 +0200 [thread overview] Message-ID: <CALWbr2zJFjbaCdA3d1eaFuP4HGShAwnK=gisRD=KHKWWi-XuTg@mail.gmail.com> (raw) In-Reply-To: <CADL+T9ax0maws3GR24YV77Yge7knqHd5mfuPd_AqE9b4UmvYPg@mail.gmail.com> On Tue, Jul 2, 2013 at 10:34 PM, Ed Hutchins <email@example.com> wrote: > On the other hand > trying to figure > out the history of events from a large directed graph of commits > without any clue about > what topics first spawned each commit is actively harmful in many > cases (trying to display > a clear history of who did what for what reasons, for example). I think this is exactly what Junio does with git.git: - Each branch is named "$initials/$topicname" before being merged. - Branches are always merged with --no-ff. I think it answers your question: Who (initials) does what (topic) The name of the branch is also stuck as part of the history as the merge reads the name of the merged branch: e.g. Merge branch 'rr/remote-branch-config-refresh' You can of course provide more information than the simple commit header line (that would give the "what reasons"). Of course, it's even easier to read if you always merge in the same direction (that allows you to easily find the first commit of the branch). Hope that helps, Antoine
next prev parent reply other threads:[~2013-07-03 16:16 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-02 19:37 Ed Hutchins 2013-07-02 19:49 ` Fredrik Gustafsson 2013-07-02 20:00 ` Junio C Hamano 2013-07-02 20:34 ` Ed Hutchins 2013-07-03 16:16 ` Antoine Pelisse [this message] 2013-07-03 17:31 ` Ed Hutchins 2013-07-03 18:19 ` Junio C Hamano 2013-07-04 0:00 ` Andrew Ardill 2013-07-02 20:31 ` Johan Herland 2013-07-03 9:33 ` Matthieu Moy 2013-07-03 15:47 ` Ed Hutchins 2013-07-03 18:08 ` Junio C Hamano 2013-07-03 23:46 ` Feature request: Jakub Narebski 2013-07-03 23:52 ` Dany 2013-07-03 23:53 ` Dany 2013-07-04 8:08 ` Matthieu Moy 2013-07-09 21:46 ` Feature request: "author branch" in commit object Philip Oakley
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CALWbr2zJFjbaCdA3d1eaFuP4HGShAwnK=gisRD=KHKWWi-XuTg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Feature request: "author branch" in commit object' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).