From: "Dan McGee" <dpmcgee@gmail.com>
To: git@vger.kernel.org
Subject: Update local tracking refs when pushing- no way to disable
Date: Thu, 5 Jul 2007 20:22:04 -0400 [thread overview]
Message-ID: <449c10960707051722q6650ec7dq6012695acdfba4af@mail.gmail.com> (raw)
In this commit:
b516968ff62ec153e008d033c153affd7ba9ddc6
I don't know if anyone else has the same way of working as I do, but I
tend to set the "remote.<name>.skipDefaultUpdate" property to true for
my publicly visible repository, just so I don't have duplicate branch
heads lying around in my local repository. Call this peculiar, but I
like it that way. However, git-push does not respect this property,
meaning I know have these branches whether I want them or not. In a
tool such as qgit or even 'git branch -a' output, it starts to get
awful cluttered.
I'm not terribly familiar with GIT internals, so I don't know that I
am the best to make a patch for this, but I'll take no response as a
answer that I should start coding something up. Please CC me on
emails, I'm not on the GIT mailing list.
-Dan
next reply other threads:[~2007-07-06 0:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 0:22 Dan McGee [this message]
2007-07-06 1:17 ` Update local tracking refs when pushing- no way to disable Johannes Schindelin
2007-07-06 1:31 ` Junio C Hamano
2007-07-06 3:37 ` Daniel Barkalow
2007-07-06 8:26 ` Marco Costalba
2007-07-06 8:42 ` Shawn O. Pearce
2007-07-06 12:46 ` Johannes Schindelin
2007-07-06 18:56 ` Daniel Barkalow
2007-07-06 18:59 ` Johannes Schindelin
2007-07-06 19:20 ` Daniel Barkalow
2007-07-06 19:46 ` Johannes Schindelin
2007-07-06 13:20 ` Dan McGee
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=449c10960707051722q6650ec7dq6012695acdfba4af@mail.gmail.com \
--to=dpmcgee@gmail.com \
--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).