public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: Proposal to change branch maintenance
Date: Mon, 18 Feb 2013 16:11:00 -0000	[thread overview]
Message-ID: <87fw0td2la.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3y5elq1yk.fsf@redhat.com> (Sergio Durigan Junior's message of "Mon, 18 Feb 2013 08:46:27 -0300")

Sergio> I would like to propose another thing: the archer repository should
Sergio> accept "git push --force".  It is annoying having to delete & re-create
Sergio> the branch you're working on because you're using git-rebase to maintain
Sergio> a series of patches.  Maybe we could talk to Jim about that?

We can edit the git config file on sourceware ourselves.

I'm ok with changing this.
Anybody else have comments on it?

Tom

  reply	other threads:[~2013-02-18 16:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 21:56 Tom Tromey
2013-02-13 11:32 ` Gary Benson
2013-02-13 12:16 ` Jan Kratochvil
2013-02-13 12:33   ` Pedro Alves
2013-02-13 12:53   ` Gary Benson
2013-02-18 16:10   ` Tom Tromey
2013-02-18 16:20     ` Jan Kratochvil
2013-02-18 16:29       ` Tom Tromey
2013-02-18 17:03         ` Jan Kratochvil
2013-02-18 17:40           ` Tom Tromey
2013-02-18 22:01           ` Tom Tromey
2013-02-22 15:54             ` Tom Tromey
2013-02-26 17:33     ` Tom Tromey
2013-02-26 20:13       ` Tom Tromey
2013-02-26 20:31         ` Sergio Durigan Junior
2013-02-27 20:50           ` Tom Tromey
2013-02-27 20:50         ` Tom Tromey
2013-02-27 21:15           ` Tom Tromey
2013-02-18 11:46 ` Sergio Durigan Junior
2013-02-18 16:11   ` Tom Tromey [this message]
2013-02-18 16:16     ` Jan Kratochvil
2013-02-22 15:06       ` Tom Tromey
2013-02-22 21:27 ` Tom Tromey

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=87fw0td2la.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=sergiodj@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).