From: Ed Hutchins <email@example.com> To: Junio C Hamano <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Feature request: "author branch" in commit object Date: Tue, 2 Jul 2013 13:34:05 -0700 [thread overview] Message-ID: <CADL+T9ax0maws3GR24YV77Yge7knqHd5mfuPd_AqE9b4UmvYPg@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> I'm not sure I follow how it could be actively harmful? I would think the "author branch" nomenclature (as opposed to just calling it "branch") along with clear documentation that these values are just captures of the particular state the commit was authored from would more than assuage any potential misuse. 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). On Tue, Jul 2, 2013 at 1:00 PM, Junio C Hamano <email@example.com> wrote: > Ed Hutchins <firstname.lastname@example.org> writes: > >> I realize that branch names are ephemeral repo-specific things, but it >> would be really useful to be able to determine what branch a commit >> was authored from (as a hint to ancestry graph layout tools, for >> example). > > Hmm. I think the current thinking so far is that it is harmful to > engrave that information in the commit object, exactly for the > reason you stated upfront: these names are local in the repository > the commit was created, and do not have any global meaning. > >> Is there any way to do this currently, is it planned, or >> would it be deemed useful enough to be worth adding to each commit >> object? > > No, no, and no, not because it is not just useful enough but it may > be actively harmful.
next prev parent reply other threads:[~2013-07-02 20:34 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 [this message] 2013-07-03 16:16 ` Antoine Pelisse 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=CADL+T9ax0maws3GR24YV77Yge7knqHd5mfuPd_AqE9b4UmvYPg@mail.gmail.com \ --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).