git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Michael Witten <mfwitten@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Improvement?] How do you switch branches in a bare repo?
Date: Fri, 12 Mar 2010 10:48:36 -0600	[thread overview]
Message-ID: <20100312164835.GA2303@progeny.tock> (raw)
In-Reply-To: <b4087cc51003120009o7bd99609w996de02b732fbbd9@mail.gmail.com>

Michael Witten wrote:

> Commands like "git checkout" and "git reset" essentially operate on 2
> aspects of a repository:
> 
>     (1) The repository's state.
>     (2) The repository's working tree.
> 
> Is there any reason why these commands can't just operate on (1) in a
> bare repository, thereby allowing users to use familiar commands to
> get their work done?

Not that I can think of.  I’d say go for it.  (I’ll be glad to help in
any way I can.  Not sure I’ll have much time soon, but I can answer
questions, look over patches, and so on.)

> The "git checkout" command in a bare repository should serve to select
> on which branch other commands (like "git reset") operate, etc.

My only worry would be low-level scripts that want to be able to use a
separate index or work tree with a bare repository.  Maybe the index
file could be in a special "bare" state to request the semantics
you’re describing.

Jonathan

  reply	other threads:[~2010-03-12 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12  6:26 How do you switch branches in a bare repo? Adam Nielsen
2010-03-12  6:57 ` Johannes Sixt
2010-03-12  7:12   ` Adam Nielsen
2010-03-12  7:34     ` Johannes Sixt
2010-03-12  7:38       ` Adam Nielsen
2010-03-12  8:09 ` [Improvement?] " Michael Witten
2010-03-12 16:48   ` Jonathan Nieder [this message]
2010-03-14  6:52   ` Junio C Hamano

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=20100312164835.GA2303@progeny.tock \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mfwitten@gmail.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 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 NNTP newsgroup(s).