git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: hoegsberg@gmail.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH] branch as a builtin (again)
Date: Mon, 21 Aug 2006 04:03:45 -0400	[thread overview]
Message-ID: <20060821080345.GA26191@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0608210045450.17336@chino.corp.google.com>

> On Sun, 20 Aug 2006, Kristian Høgsberg wrote:
> > diff --git a/builtin-branch.c b/builtin-branch.c
> > +static const char builtin_branch_usage[] =
> > +    "git-branch [(-d | -D) <branchname>] | [[-f] <branchname> [<start-point>]] | -r";

What happened to the -l switch to create a reflog for the new branch?

> > +static void delete_branches(int argc, const char **argv, int force)

What happened to deleting the reflog when the branch gets deleted?


In both cases please see the existing git-branch documentation and
shell script.

I applaud the effort of removing some of these smaller shell scripts
with more portable C code but at the same time I'd hate to see a
loss of functionality, especially something that I use!  :-)

-- 
Shawn.

  reply	other threads:[~2006-08-21  8:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-20 21:22 [PATCH] branch as a builtin (again) Kristian Høgsberg
2006-08-20 23:55 ` Johannes Schindelin
2006-08-21  7:49 ` David Rientjes
2006-08-21  8:03   ` Shawn Pearce [this message]
2006-08-21 10:13 ` Jonas Fonseca
2006-08-21 20:12   ` Kristian Høgsberg
2006-08-21 20:23     ` David Rientjes
2006-08-21 20:45       ` Kristian Høgsberg
2006-08-22  7:00         ` Junio C Hamano
2006-08-21 20:27     ` Johannes Schindelin
2006-08-21 21:07       ` Kristian Høgsberg
     [not found]       ` <59ad55d30608211337jabd515bra3566fbd0f7ba5a0@mail.gmail.com>
2006-08-21 21:25         ` Johannes Schindelin
2006-08-21 20:41     ` Shawn Pearce

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=20060821080345.GA26191@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=hoegsberg@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).