git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: git@vger.kernel.org
Subject: Re: git-gui Error
Date: Wed, 14 Feb 2007 21:40:14 -0500	[thread overview]
Message-ID: <20070215024014.GA29865@spearce.org> (raw)
In-Reply-To: <20070214174635.GA21612@auto.tuwien.ac.at>

Martin Koegler <mkoegler@auto.tuwien.ac.at> wrote:
> I'm missing the possibility to base a new branch on a tag.
> The following adds a tag drop down to the new branch dialog:

Yea, again, laziness on my part.  :-) You could enter the tag name
in the SHA-1 expression field, but having it as a picklist may
make sense.
 
> --- git-gui.sh  2007-02-14 08:51:38.025781229 +0000
> +++ git-gui     2007-02-14 10:50:13.618870598 +0000
> @@ -1916,11 +1916,25 @@
>         return [lsort -unique $all_trackings]
>  }

Unfortunately this patch has severe whitespace damage.  All of the
tabs were received here as spaces, so nothing applies.

>  proc do_create_branch_action {w} {
>         global all_heads null_sha1 repo_config
>         global create_branch_checkout create_branch_revtype
>         global create_branch_head create_branch_trackinghead
>         global create_branch_name create_branch_revexp
> +        global create_branch_tag

The indentation does not line up here.  All of the existing context
lines were indented with just one tab, until the whitespace damage
noted above.

-- 
Shawn.

  reply	other threads:[~2007-02-15  2:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13  6:56 git-gui Error Martin Koegler
2007-02-13  7:45 ` Shawn O. Pearce
2007-02-13 21:53   ` Martin Koegler
2007-02-14  2:22     ` Shawn O. Pearce
2007-02-14  6:00       ` Shawn O. Pearce
2007-02-14 17:46         ` Martin Koegler
2007-02-15  2:40           ` Shawn O. Pearce [this message]
2007-02-15  6:07             ` Martin Koegler
2007-02-15  6:38               ` Shawn O. Pearce
2007-02-14 18:09       ` Martin Koegler
2007-02-15  4:07         ` Shawn O. 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=20070215024014.GA29865@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=mkoegler@auto.tuwien.ac.at \
    /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).