Brett Cannon wrote:
> Because other core devs wanted a linear history. This preference was very
> strong to the point people were willing to forgo the Merge button in
> GitHub's web UI to enforce it until GitHub added the squash merge support
> for the Merge button.
Actually, there's a third optio
On Wed, Feb 8, 2017 at 8:52 AM, Senthil Kumaran wrote:
> On Tue, Feb 7, 2017 at 11:38 PM, Victor Stinner
> wrote:
> > I know that different people have different expectation on GitHub. I
> > would like to take the opportunity of migrating to Git to use the
> > "author" and "committer" fields. If
On Wed, 8 Feb 2017 at 15:04 Victor Stinner wrote:
> 2017-02-08 23:42 GMT+01:00 Brett Cannon :
> > Don't forget we are doing squash merges,
>
> Ah, I didn't know. Why not using merges?
>
Because other core devs wanted a linear history. This preference was very
strong to the point people were will
On 09.02.2017 00:03, Victor Stinner wrote:
2017-02-08 23:42 GMT+01:00 Brett Cannon :
Don't forget we are doing squash merges,
Ah, I didn't know. Why not using merges?
Same question here. I see no benefit just overhead, mistakes and longer
processes.
Sven
_
2017-02-08 23:42 GMT+01:00 Brett Cannon :
> Don't forget we are doing squash merges,
Ah, I didn't know. Why not using merges?
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
On Wed, 8 Feb 2017 at 13:33 Victor Stinner wrote:
> 2017-02-08 21:32 GMT+01:00 Terry Reedy :
> > Many patches have multiple authors. Does the 'author' field allow that?
> > Often, the committer adds missing chunks or rewrites the work with
> various
> > degrees of editing. Sometimes a read a pat
2017-02-08 21:32 GMT+01:00 Terry Reedy :
> Many patches have multiple authors. Does the 'author' field allow that?
> Often, the committer adds missing chunks or rewrites the work with various
> degrees of editing. Sometimes a read a patch for the idea and then start
> fresh with the actual code.
On Wed, 8 Feb 2017 at 12:33 Terry Reedy wrote:
> On 2/8/2017 2:38 AM, Victor Stinner wrote:
>
> > I know that different people have different expectation on GitHub. I
> > would like to take the opportunity of migrating to Git to use the
> > "author" and "committer" fields. If the author is set to
On 2/8/2017 2:38 AM, Victor Stinner wrote:
I know that different people have different expectation on GitHub. I
would like to take the opportunity of migrating to Git to use the
"author" and "committer" fields. If the author is set to the real
author, the one who proposed the change on the bug t
On Tue, 7 Feb 2017 at 23:38 Victor Stinner wrote:
> 2017-02-08 8:35 GMT+01:00 Victor Stinner :
> > I'm sure the patch author would appreciate it, but I don't think we
> > need to require it as we have gone this long without it.
>
> I know that different people have different expectation on GitHub
On Tue, Feb 7, 2017 at 11:38 PM, Victor Stinner
wrote:
> I know that different people have different expectation on GitHub. I
> would like to take the opportunity of migrating to Git to use the
> "author" and "committer" fields. If the author is set to the real
> author, the one who proposed the c
2017-02-08 8:35 GMT+01:00 Victor Stinner :
> I'm sure the patch author would appreciate it, but I don't think we
> need to require it as we have gone this long without it.
I know that different people have different expectation on GitHub. I
would like to take the opportunity of migrating to Git to
(Oops, I wrote privately to Brett, so he replied me in private. So
here is a copy of our emails.)
Brett Cannon via gmail.com
On Tue, 7 Feb 2017 at 13:42 Victor Stinner wrote:
>
> If I push a patch file written by someone else, should I try to use the
> author full name + email?
I'm sure the pat
On Tue, 7 Feb 2017 at 11:17 Jim F.Hilliard wrote:
> That's great, congratulations! I believe this change will make it way
> easier for people to get involved!
>
> A small question, since people can now submit new issues via pulls instead
> of going to bugs.python.org, what will be the purpose of
Nice, good news.
On 02/07, Brett Cannon wrote:
To let the non-core devs know, the GitHub migration will be happening this
Friday. For those of you who use the current GitHub mirror to create
patches, do be aware that the hashes will most likely be changing so don't
expect your checkout to work
That's great, congratulations! I believe this change will make it way
easier for people to get involved!
A small question, since people can now submit new issues via pulls instead
of going to bugs.python.org, what will be the purpose of the latter?
As I skimmed through cpython-devguide.readthedoc
2017-02-07 10:03 GMT-08:00 Brett Cannon :
> To let the non-core devs know, the GitHub migration will be happening this
> Friday. For those of you who use the current GitHub mirror to create
> patches, do be aware that the hashes will most likely be changing so don't
> expect your checkout to work
To let the non-core devs know, the GitHub migration will be happening this
Friday. For those of you who use the current GitHub mirror to create
patches, do be aware that the hashes will most likely be changing so don't
expect your checkout to work past Thursday (you can always generate a patch
and
18 matches
Mail list logo
