From: Junio C Hamano <gitster@pobox•com>
To: Nico Williams <nico@cryptonector•com>
Cc: "Theodore Ts'o" <tytso@mit•edu>,
Jonathan Nieder <jrnieder@gmail•com>,
git discussion list <git@vger•kernel.org>,
Ronnie Sahlberg <sahlberg@google•com>
Subject: Re: Use case (was Re: Should branches be objects?)
Date: Wed, 25 Jun 2014 10:42:49 -0700 [thread overview]
Message-ID: <xmqqegycans6.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAK3OfOgb3zt0HKkeQKfMR9u7sKRzjCZAeOQh=qSyt9cVordG4A@mail.gmail.com> (Nico Williams's message of "Wed, 25 Jun 2014 00:29:50 -0500")
Nico Williams <nico@cryptonector•com> writes:
> On Tue, Jun 24, 2014 at 6:09 AM, Theodore Ts'o <tytso@mit•edu> wrote:
> ...
>> This seems pretty close to what we have with signed tags. When I send
>> a pull request to Linus, I create a signed tag which createscontains a
>> message about a set of commits, and this message is automatically
>> included in the pull request message generated with "git
>> request-pull", and when Linus merges my pull request, the
>> cryptographically signed tag, along with the message, date of the
>> signature, etc., is preserved for all posterity.
>
> Thanks for pointing this out. Signed tags are objects -- that's a
> clear and strong precedent..
Sounds as if you are interpreting what Ted said as a supporting
argument for having branches as separate type of objects, but the
way I read it was "signed tags are sufficient for what you want to
do; adding a new "branch" type does not make much sense at this
point".
next prev parent reply other threads:[~2014-06-25 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 3:20 Use case (was Re: Should branches be objects?) Nico Williams
2014-06-24 11:01 ` John Keeping
2014-06-24 11:09 ` Theodore Ts'o
2014-06-25 5:29 ` Nico Williams
2014-06-25 17:42 ` Junio C Hamano [this message]
2014-06-25 22:44 ` Theodore Ts'o
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqegycans6.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=nico@cryptonector$(echo .)com \
--cc=sahlberg@google$(echo .)com \
--cc=tytso@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox