From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: palves@redhat.com, tromey@redhat.com, gbenson@redhat.com,
stanshebs@earthlink.net, gdb@sourceware.org
Subject: Re: Patchwork patch tracking system
Date: Wed, 21 May 2014 18:48:00 -0000 [thread overview]
Message-ID: <83tx8jm0hx.fsf@gnu.org> (raw)
In-Reply-To: <20140521182349.GR22794@adacore.com>
> Date: Wed, 21 May 2014 11:23:49 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Pedro Alves <palves@redhat.com>, tromey@redhat.com, gbenson@redhat.com,
> stanshebs@earthlink.net, gdb@sourceware.org
>
> > Does this mean I cannot push after merging from my local branch into
> > master in my repository? IOW, if I have local feature branches, do I
> > have to rebase commits from those branches before pushing them?
>
> We do not have any hook that would reject such a push, but we would
> _really_ like you to
Too bad.
> (this is going back to a discussion we had about allowing merge
> commits or not).
AFAIR, that discussion was about merging from the (public) release
branch to master. Now I asked about my private branches, which is
slightly different.
next prev parent reply other threads:[~2014-05-21 18:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 10:08 Gary Benson
2014-04-04 22:50 ` Stan Shebs
2014-04-17 18:18 ` Gary Benson
2014-04-22 15:40 ` Joel Brobecker
2014-04-22 15:51 ` Eric Christopher
2014-04-22 18:37 ` Joel Brobecker
2014-04-24 11:42 ` Siva Chandra
2014-08-02 14:25 ` Mike Frysinger
2014-04-29 17:25 ` Tom Tromey
2014-04-29 17:36 ` Eli Zaretskii
2014-04-29 18:58 ` Joel Brobecker
2014-04-30 9:19 ` Gary Benson
2014-04-30 12:45 ` Joel Brobecker
2014-04-29 19:33 ` Pedro Alves
2014-04-29 22:32 ` Breazeal, Don
2014-04-30 1:08 ` Pedro Alves
2014-04-30 3:45 ` Breazeal, Don
2014-05-21 14:47 ` Tom Tromey
2014-05-21 17:18 ` Pedro Alves
2014-05-21 17:49 ` Joel Brobecker
2014-05-21 18:03 ` Eli Zaretskii
2014-05-21 18:23 ` Joel Brobecker
2014-05-21 18:48 ` Eli Zaretskii [this message]
2014-05-21 19:45 ` Joel Brobecker
2014-05-21 21:35 ` Pedro Alves
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=83tx8jm0hx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gbenson@redhat.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=stanshebs@earthlink.net \
--cc=tromey@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