Hi!
On Tue, Jun 16, 2020 at 02:09:37PM +0100, Jonathan Wakely wrote:
> I see no harm in rebasing public branches as long as nobody expects
> otherwise. A public branch on gcc.gnu.org under refs/heads that is
> being pulled by unknown persons and used in unknown forks for unknown
> purposes shouldn
On Tue, Jun 16, 2020 at 02:54:13PM +, Joseph Myers wrote:
> On Tue, 16 Jun 2020, Jonathan Wakely via Gcc wrote:
>
> > I see no harm in rebasing public branches as long as nobody expects
> > otherwise.
>
> And by design you *can* rebase user and vendor branches (but not those in
> other names
On Tue, 16 Jun 2020, Jonathan Wakely via Gcc wrote:
> I see no harm in rebasing public branches as long as nobody expects
> otherwise.
And by design you *can* rebase user and vendor branches (but not those in
other namespaces). The message about not being a fast-forward is just a
warning, not
Hi!
On Tue, Jun 16, 2020 at 11:11:01AM +0200, Martin Jambor wrote:
> On Mon, Jun 15 2020, Segher Boessenkool wrote:
> > What.
> >
> > Of course it is not a fast-forward. I rebase the branches I publish,
> > what is the point of publishing them otherwise? This is so that people
> > can see the st
On Tue, 16 Jun 2020 at 10:11, Martin Jambor wrote:
>
> Hi,
>
> On Mon, Jun 15 2020, Segher Boessenkool wrote:
> > Hi!
> >
> [...]
> > What.
> >
> > Of course it is not a fast-forward. I rebase the branches I publish,
> > what is the point of publishing them otherwise? This is so that people
> >
Hi,
On Mon, Jun 15 2020, Segher Boessenkool wrote:
> Hi!
>
[...]
> What.
>
> Of course it is not a fast-forward. I rebase the branches I publish,
> what is the point of publishing them otherwise? This is so that people
> can see the stuff that will make its way into master *later*.
>
> The numbe
On Jun 15 2020, Segher Boessenkool wrote:
> $ git push fsf :refs/users/segher/heads/cc0
or git push --delete fsf refs/users/segher/heads/cc0
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something complet
On Mon, Jun 15, 2020 at 09:17:43PM +0200, Richard Biener wrote:
> On June 15, 2020 7:19:13 PM GMT+02:00, Joseph Myers
> wrote:
> >I don't know if deleting and then recreating a user branch (in separate
> >
> >pushes) avoids the limit (and the excess mails) in the case where a
> >user
> >branch i
On June 15, 2020 7:19:13 PM GMT+02:00, Joseph Myers
wrote:
>On Mon, 15 Jun 2020, Segher Boessenkool wrote:
>
>> It should never send email for things that are on master (or any
>release
>> branch) already.
>
>https://github.com/AdaCore/git-hooks/issues/9
>
>https://github.com/AdaCore/git-hooks/pu
David,
The currently implemented rules and automation are not
encouraging personal branches in the GCC repository.
You are hereby awarded the prize for the understatement of the month.
On Mon, Jun 15, 2020 at 2:13 PM Segher Boessenkool
wrote:
>
> On Mon, Jun 15, 2020 at 10:47:48AM -0700, H.J. Lu wrote:
> > These are all the reasons why I don't use GCC repo for my personal
> > branches.
>
> Yeah, but I thought a lot of different GCC people might be interested in
> my "nuke CC0" p
On Mon, Jun 15, 2020 at 10:47:48AM -0700, H.J. Lu wrote:
> These are all the reasons why I don't use GCC repo for my personal
> branches.
Yeah, but I thought a lot of different GCC people might be interested in
my "nuke CC0" patches, so putting it in the official repo seemed like a
good idea, for
On Mon, Jun 15, 2020 at 10:43 AM Segher Boessenkool
wrote:
>
> Hi Joseph,
>
> Thanks, good to hear things will get better.
>
> On Mon, Jun 15, 2020 at 05:19:13PM +, Joseph Myers wrote:
> > > It should never send email for user branches *at all*.
> >
> > I think sending email for all branches s
Hi Joseph,
Thanks, good to hear things will get better.
On Mon, Jun 15, 2020 at 05:19:13PM +, Joseph Myers wrote:
> > It should never send email for user branches *at all*.
>
> I think sending email for all branches showing the development taking
> place there (as opposed to commits that ar
I think you can work around by deleting the branch before pushing.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Mon, 15 Jun 2020, Segher Boessenkool wrote:
> It should never send email for things that are on master (or any release
> branch) already.
https://github.com/AdaCore/git-hooks/issues/9
https://github.com/AdaCore/git-hooks/pull/12 is marked "Approved". It
certainly has fixes for some of the i
On Mon, Jun 15, 2020 at 06:41:02PM +0200, Andreas Schwab wrote:
> On Jun 15 2020, Segher Boessenkool wrote:
>
> > On Mon, Jun 15, 2020 at 06:28:39PM +0200, Richard Biener wrote:
> >> On June 15, 2020 6:05:26 PM GMT+02:00, Segher Boessenkool
> >> wrote:
> >> >Of course it is not a fast-forward.
On Jun 15 2020, Segher Boessenkool wrote:
> On Mon, Jun 15, 2020 at 06:28:39PM +0200, Richard Biener wrote:
>> On June 15, 2020 6:05:26 PM GMT+02:00, Segher Boessenkool
>> wrote:
>> >Of course it is not a fast-forward. I rebase the branches I publish,
>> >what is the point of publishing them ot
On Mon, Jun 15, 2020 at 06:28:39PM +0200, Richard Biener wrote:
> On June 15, 2020 6:05:26 PM GMT+02:00, Segher Boessenkool
> wrote:
> >Of course it is not a fast-forward. I rebase the branches I publish,
> >what is the point of publishing them otherwise? This is so that people
> >can see the s
On June 15, 2020 6:05:26 PM GMT+02:00, Segher Boessenkool
wrote:
>Hi!
>
>$ git push -n fsf
>To git+ssh://gcc.gnu.org/git/gcc.git
> + 1db88c6...71e5e35 cc0 -> refs/users/segher/heads/cc0 (forced update)
>
>$ git push fsf
>Counting objects: 664, done.
>Delta compression using up to 64 threads.
>Com
20 matches
Mail list logo
