On Okt 21 2019, Joseph Myers wrote:
> I've seen some versions of plain "git push" in the past warn about changed
> defaults for what it pushes, so being explicit avoids confusing people
> with that warning. Though it seems that warning was removed from git in
> 2016, so maybe avoiding it is no
On Mon, 21 Oct 2019, Mike Stump wrote:
> This isn't helpful. The advanced person already knows this and the
> limitations of it, and the non-advanced people are confused by the lack
> of certainty. So, the web page should not say it, and saying it here,
> doesn't help much as well. Trying to
On Mon, Oct 21, 2019 at 08:20:33AM -0700, Mike Stump wrote:
> On Oct 21, 2019, at 3:30 AM, Segher Boessenkool
> wrote:
> >
> > On Sun, Oct 20, 2019 at 06:06:30PM +0200, Gerald Pfeifer wrote:
> >> On Wed, 9 Oct 2019, js...@gcc.gnu.org wrote:
> >>> +Use "git commit" and "git push origin
> >>> +mas
On Oct 21, 2019, at 3:30 AM, Segher Boessenkool
wrote:
>
> On Sun, Oct 20, 2019 at 06:06:30PM +0200, Gerald Pfeifer wrote:
>> On Wed, 9 Oct 2019, js...@gcc.gnu.org wrote:
>>> +Use "git commit" and "git push origin
>>> +master" to check in the patch.
>>
>> I will admit I made a couple of first c
On Sun, Oct 20, 2019 at 06:06:30PM +0200, Gerald Pfeifer wrote:
> On Wed, 9 Oct 2019, js...@gcc.gnu.org wrote:
> > +Use "git commit" and "git push origin
> > +master" to check in the patch.
>
> I will admit I made a couple of first commits without reading those
> details and just used a plain "git
On Wed, 9 Oct 2019, js...@gcc.gnu.org wrote:
> +Use "git commit" and "git push origin
> +master" to check in the patch.
I will admit I made a couple of first commits without reading those
details and just used a plain "git push".
Is there any problem with that, any drawback?
Or could we simpli
