From: Jonathan Nieder <jrnieder@gmail.com>
To: Nico Williams <nico@cryptonector.com>
Cc: git@vger.kernel.org, Ronnie Sahlberg <sahlberg@google.com>
Subject: Re: Should branches be objects?
Date: Thu, 19 Jun 2014 16:46:14 -0700 [thread overview]
Message-ID: <20140619234614.GY8557@google.com> (raw)
In-Reply-To: <CAK3OfOiB0YWf25Hvvvqi+YBwu2V-gE-sjm7XrfE0p2zds4CE2Q@mail.gmail.com>
Hi,
Nico Williams wrote:
> - one could see the history of branches, including
Interesting. 'git log -g' is good for getting that information
locally, but the protocol doesn't have a way to get it from a remote
server so you have to ssh in. Ronnie (cc-ed) and I were talking
recently about whether it would make sense to update git protocol to
have a way to get at the remote reflogs more easily --- would that be
useful to you?
> - how commits were grouped when pushed/pulled (push 5 commits, and
> the branch object will record that its head moved by those five
> commits at once)
The reflog on the server (if enabled) records this.
> - rebase history (git log <branch-object> -> better than git reflog!)
The local reflog ('git log -g <branch>') records this.
> - object transactional APIs would be used to update branches
Ronnie's recent ref-transaction code does this.
Thanks and hope that helps,
Jonathan
next prev parent reply other threads:[~2014-06-19 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 21:37 Should branches be objects? Nico Williams
2014-06-19 23:46 ` Jonathan Nieder [this message]
2014-06-20 0:25 ` Nico Williams
2014-06-20 0:31 ` Nico Williams
2014-06-20 1:01 ` Jonathan Nieder
2014-06-20 2:27 ` Jeff King
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=20140619234614.GY8557@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@cryptonector.com \
--cc=sahlberg@google.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.