Merge lp:~mbp/bzr/484558-merge-directory into lp:bzr
| Status: | Work in progress |
|---|---|
| Proposed branch: | lp:~mbp/bzr/484558-merge-directory |
| Merge into: | lp:bzr |
| Diff against target: |
132 lines (+27/-34) (has conflicts) 4 files modified
NEWS (+10/-0) bzrlib/bundle/__init__.py (+17/-5) bzrlib/tests/test_http.py (+0/-8) bzrlib/tests/test_read_bundle.py (+0/-21) Text conflict in NEWS Text conflict in bzrlib/bundle/__init__.py |
| To merge this branch: | bzr merge lp:~mbp/bzr/484558-merge-directory |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| John A Meinel | 2010-03-30 | Approve on 2010-03-30 | |
|
Review via email:
|
|||
Description of the Change
According to https:/
| John Szakmeister (jszakmeister) wrote : | # |
| John A Meinel (jameinel) wrote : | # |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John Szakmeister wrote:
> On Tue, Mar 30, 2010 at 2:00 AM, Martin Pool <email address hidden> wrote:
> [snip]
>> +<<<<<<< TREE
>> * Added ``cachedproperty`` decorator to ``bzrlib.
>> (Andrew Bennetts)
>>
>> +=======
>> +* Delete deprecated function ``read_
>> + (Martin Pool)
>> +
>> +>>>>>>> MERGE-SOURCE
>
> It looks like conflict markers snuck in there.
>
>> * Many test features were renamed from ``FooFeature`` to ``foo_feature``
>> to be consistent with instances being lower case and classes being
>> CamelCase. For the features that were more likely to be used, we added a
>>
>> === modified file 'bzrlib/
>> --- bzrlib/
>> +++ bzrlib/
>> @@ -1,4 +1,8 @@
>> +<<<<<<< TREE
>> # Copyright (C) 2005-2010 Canonical Ltd
>> +=======
>> +# Copyright (C) 2005, 2006, 2010 Canonical Ltd
>> +>>>>>>> MERGE-SOURCE
>
> And here too. Although, is that right? How'd did it go from
> 2005-2010 to 2005, 2006, 2010?
>
> -John
I don't know if he is using my plugin, but it tracks when the file was
actually touched. It is certainly possible that we didn't modify it in
2007/2008/2009.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAku
pTkAn2ncTZRMyNx
=MFc/
-----END PGP SIGNATURE-----
| John A Meinel (jameinel) wrote : | # |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Pool wrote:
> Martin Pool has proposed merging lp:~mbp/bzr/484558-merge-directory into lp:bzr.
>
> Requested reviews:
> bzr-core (bzr-core)
> Related bugs:
> #484558 bzr 2.0.0 hang on merge & pull from location when trying to read directory as a file
> https:/
>
>
> According to https:/
>
Only concern is FTP, which I think pretends stat is available, but I'm
not sure what data it returns is actually reliable. (I know it does bad
things with mode bits, for example.)
Anyway, this looks good in general.
merge: approve
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAku
wxgAniSrCUUoYah
=92K0
-----END PGP SIGNATURE-----
| Martin Pool (mbp) wrote : | # |
> On Tue, Mar 30, 2010 at 2:00 AM, Martin Pool <email address hidden> wrote:
> [snip]
> > +<<<<<<< TREE
> > * Added ``cachedproperty`` decorator to ``bzrlib.
> > (Andrew Bennetts)
> >
> > +=======
> > +* Delete deprecated function ``read_
> > + (Martin Pool)
> > +
> > +>>>>>>> MERGE-SOURCE
>
> It looks like conflict markers snuck in there.
No, it's actually that Launchpad is doing merge --preview and telling us there will be conflicts if it's merged. I need to resolve them by merging trunk before submitting.
> > === modified file 'bzrlib/
> > --- bzrlib/
> > +++ bzrlib/
> > @@ -1,4 +1,8 @@
> > +<<<<<<< TREE
> > # Copyright (C) 2005-2010 Canonical Ltd
> > +=======
> > +# Copyright (C) 2005, 2006, 2010 Canonical Ltd
> > +>>>>>>> MERGE-SOURCE
>
> And here too. Although, is that right? How'd did it go from
> 2005-2010 to 2005, 2006, 2010?
I manually added 2010 to the list. In trunk somebody did a bulk update to the dash format.
| Martin Pool (mbp) wrote : | # |
> Only concern is FTP, which I think pretends stat is available, but I'm
> not sure what data it returns is actually reliable. (I know it does bad
> things with mode bits, for example.)
That's a really good point: if it says things that are really directories are files, we could end up not being able to merge from ftp branches, which would certainly suck - previously we would have just tried it. Similarly for http for that matter.
Perhaps we should be specifically checking "is the type known and is it not a directory" and then we can allow some transports to give noncommittal answers.
Given the only report of this bug has gone away perhaps we should reject this.
Unmerged revisions
- 4964. By Martin Pool on 2010-01-15
-
Check first whether a bundle location is a directory
- 4963. By Martin Pool on 2010-01-15
-
Remove tests for read_bundle_
from_url - 4962. By Martin Pool on 2010-01-14
-
Delete deprecated read_bundle_
from_url

On Tue, Mar 30, 2010 at 2:00 AM, Martin Pool <email address hidden> wrote: decorators` `. bundle_ from_url` `
[snip]
> +<<<<<<< TREE
> * Added ``cachedproperty`` decorator to ``bzrlib.
> (Andrew Bennetts)
>
> +=======
> +* Delete deprecated function ``read_
> + (Martin Pool)
> +
> +>>>>>>> MERGE-SOURCE
It looks like conflict markers snuck in there.
> * Many test features were renamed from ``FooFeature`` to ``foo_feature`` bundle/ __init_ _.py' bundle/ __init_ _.py 2010-02-17 17:11:16 +0000 bundle/ __init_ _.py 2010-03-30 06:00:48 +0000
> to be consistent with instances being lower case and classes being
> CamelCase. For the features that were more likely to be used, we added a
>
> === modified file 'bzrlib/
> --- bzrlib/
> +++ bzrlib/
> @@ -1,4 +1,8 @@
> +<<<<<<< TREE
> # Copyright (C) 2005-2010 Canonical Ltd
> +=======
> +# Copyright (C) 2005, 2006, 2010 Canonical Ltd
> +>>>>>>> MERGE-SOURCE
And here too. Although, is that right? How'd did it go from
2005-2010 to 2005, 2006, 2010?
-John