From: Luciano Rocha <luciano@eurotux.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: commit 0? (or: create new empty branch)
Date: Tue, 11 Mar 2008 14:45:15 +0000 [thread overview]
Message-ID: <20080311144515.GB12258@bit.office.eurotux.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0803111350550.3873@racer.site>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On Tue, Mar 11, 2008 at 01:52:00PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 11 Mar 2008, Luciano Rocha wrote:
>
> > I'd like to create a new branch, without any pre-existing data, for
> > purposes similar to git's html/man/.....
>
> If there is nothing to branch from, there is nothing to branch from.
>
> You might want to rename your branch (once you have something).
>
> But then, I do not even understand why you bother. You can always push to
> a branch of a different name, and have your principal branch being
> "master" locally.
It's not a matter of pushing/pulling. I'm referring to local branches
only.
What I'd like to have is, using util-linux-ng as an example:
branch master: util-linux-ng plus local patches
branch vendor: util-linux-ng upstream
branch metadata: information on util-linux-ng, how to compile,
dependencies, etc.
I'd have no problems with the first branches. But when I wanted to
create the third, that shares no files with the others, I stumbled with
the problem of creating a clean branch. I really didn't want to create a
branch them do "git rm .".
Johannes's tricks did the thing. Thank you all.
Regards,
Luciano Rocha
--
Luciano Rocha <luciano@eurotux.com>
Eurotux Informática, S.A. <http://www.eurotux.com/>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-11 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 12:30 commit 0? (or: create new empty branch) Luciano Rocha
2008-03-11 12:52 ` Johannes Schindelin
2008-03-11 14:45 ` Luciano Rocha [this message]
2008-03-11 14:59 ` Johannes Schindelin
2008-03-11 13:08 ` Johannes Sixt
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=20080311144515.GB12258@bit.office.eurotux.com \
--to=luciano@eurotux.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).