From: Andy Whitcroft <apw@shadowen.org>
To: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
Cc: "Shawn Pearce" <spearce@spearce.org>,
Sean <seanlkml@sympatico.ca>, "Junio C Hamano" <junkio@cox.net>,
"Miles Bader" <miles@gnu.org>,
git@vger.kernel.org, "Karl Hasselström" <kha@treskal.com>
Subject: Re: git bug? + question
Date: Mon, 06 Nov 2006 09:53:58 +0000 [thread overview]
Message-ID: <454F0636.1060406@shadowen.org> (raw)
In-Reply-To: <200611041852.23867.Josef.Weidendorfer@gmx.de>
Josef Weidendorfer wrote:
> On Saturday 04 November 2006 06:03, Shawn Pearce wrote:
>> After reading your reply you are probably correct. I can see there
>> may be workflows that want every remote branch also created as a
>> local branch.
>>
>> I could certainly live with a command line option to clone, e.g.:
>>
>> git clone --only vmdvt,vmtip user@host:/path...
>
> Still missing here: What branch should be checked out after
> cloning?
Does any need to be checked out? Or perhap I should put it another way,
when we make a virgin repository we default to master checked out but
its not joined to the DAG. Perhaps we can just init-db and fetch the
specified branches and we are done. The user will then checkout things
as they need and if they do not need master they can lose it.
>
> Perhaps it is better to extend git-checkout to allow to do the
> correct thing when the user specifies a read-only branch from
> refs/remotes. E.g. with refs/remotes/origin/vmdvt,
>
> git checkout origin/vmdvt
>
> should create a new local branch refs/heads/vmdvt which forks
> from remotes/origin/vmdvt (and abort with
> error if refs/heads/vmdvt already exists without being the local
> development branch for remotes/origin/vmdvt), add to .git/config
>
> [branch "vmdvt"]
> remote = origin
> merge = remotes/origin/vmdvt
>
> and switch to this new created branch.
>
> Given this addition to git-checkout, the implicit default
> action after cloning with --use-separate-remote should be
>
> git checkout origin/master
>
> where "master" can be changed on the git-clone command line
> to another branch, e.g. "--checkout vmdvt".
>
> IMHO, this addition to git-checkout would make it a lot
> easier to work with --use-separate-remote, as there,
> every branch other the master is read-only.
>
> And if you have two remote repositories with a master branch
> each, and you want to develop locally on both, this could
> be accomplished with
>
> git checkout -b othermaster remotes/otherrepo/master
-apw
next prev parent reply other threads:[~2006-11-06 9:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 5:56 git bug? + question Miles Bader
2006-11-03 2:40 ` Junio C Hamano
2006-11-03 3:45 ` Sean
2006-11-03 7:48 ` Karl Hasselström
2006-11-03 8:51 ` Junio C Hamano
2006-11-03 9:09 ` Andy Parkins
2006-11-03 19:28 ` Junio C Hamano
2006-11-03 9:46 ` Karl Hasselström
2006-11-03 17:15 ` Josef Weidendorfer
2006-11-03 17:13 ` Jakub Narebski
2006-11-03 19:06 ` Josef Weidendorfer
2006-11-04 12:03 ` Junio C Hamano
2006-11-04 17:50 ` Josef Weidendorfer
2006-11-03 9:59 ` Martin Waitz
2006-11-03 10:27 ` Santi Béjar
2006-11-03 16:10 ` Linus Torvalds
2006-11-03 19:53 ` Junio C Hamano
2006-11-03 8:53 ` Andy Parkins
[not found] ` <20061102224549.499610d1.seanlkml@sympatico.ca>
2006-11-03 8:12 ` Karl Hasselström
2006-11-03 9:25 ` Sean
[not found] ` <20061103042540.192bbd18.seanlkml@sympatico.ca>
2006-11-03 9:51 ` Karl Hasselström
2006-11-03 20:29 ` Shawn Pearce
2006-11-03 21:27 ` Sean
2006-11-03 23:29 ` Jeff King
2006-11-04 5:10 ` Shawn Pearce
[not found] ` <20061103162707.cc8af608.seanlkml@sympatico.ca>
2006-11-04 5:04 ` Shawn Pearce
2006-11-03 20:36 ` Shawn Pearce
2006-11-03 21:24 ` Sean
2006-11-04 12:03 ` Junio C Hamano
2006-11-04 15:33 ` Sean
[not found] ` <20061104103325.bfb5e33e.seanlkml@sympatico.ca>
2006-11-04 19:07 ` Shawn Pearce
[not found] ` <20061103162422.b0bf105e.seanlkml@sympatico.ca>
2006-11-04 5:03 ` Shawn Pearce
2006-11-04 17:52 ` Josef Weidendorfer
2006-11-04 19:05 ` Shawn Pearce
2006-11-06 11:05 ` Josef Weidendorfer
2006-11-06 9:53 ` Andy Whitcroft [this message]
2006-11-06 11:00 ` Josef Weidendorfer
2006-11-06 12:32 ` Andy Whitcroft
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=454F0636.1060406@shadowen.org \
--to=apw@shadowen.org \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=kha@treskal.com \
--cc=miles@gnu.org \
--cc=seanlkml@sympatico.ca \
--cc=spearce@spearce.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.
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.