From: Junio C Hamano <gitster@pobox.com>
To: Ed Hutchins <eh@demeterr.com>
Cc: git@vger.kernel.org
Subject: Re: Feature request: "author branch" in commit object
Date: Tue, 02 Jul 2013 13:00:01 -0700 [thread overview]
Message-ID: <7v38rwlola.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CADL+T9YGtvFrzStxJW64OJEV6H0BroMbkVCJdsDwWDaUWd91zQ@mail.gmail.com> (Ed Hutchins's message of "Tue, 2 Jul 2013 12:37:13 -0700")
Ed Hutchins <eh@demeterr.com> 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:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 19:37 Feature request: "author branch" in commit object Ed Hutchins
2013-07-02 19:49 ` Fredrik Gustafsson
2013-07-02 20:00 ` Junio C Hamano [this message]
2013-07-02 20:34 ` Ed Hutchins
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=7v38rwlola.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=eh@demeterr.com \
--cc=git@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).