[RFC] bzr-upload documentation

[marc gonzalez-carnicer]

thanks for the reply,

2009/4/29 Vincent Ladeuil <v.ladeuil+lp at free.fr>:
>>>>>> "mg" == marc gonzalez-carnicer <carnicer.lists at gmail.com> writes:
>
>    mg> I had approached Emma directly asking for a usage question, but after
>    mg> reading here I realize that I have had a problem interpreting both the
>    mg> built-in documentation and the tutorial.
>
>    mg> After reading, I've thought that the upload plug-in just uploaded a
>    mg> pristine export of the repository.
>
> More like an export of the working tree (with some limitations
> regarding chmod bits).

i see


>
>    mg> But after Emma response and some emails I've found here,
>    mg> it appears that what is uploaded is a working tree.
>
> Almost.
>
>    mg> This is not what I was hoping for, I wanted to upload for
>    mg> example just say revision 8, and when I tried the -r the
>    mg> program tries to upload the whole repository.
>
> That's the expected behavior if you haven't uploaded yet.


i see. may i ask, how does it behave when uploading a revision? are
the complete modified files uploaded, or it's just the diffs on these
files that are applied?

do you think it would make sense to have an option --initial-revision
make sense? this way the command would "trust" that what is already
upload matches the content of the working tree of the specified
revision, making it unnecessary to upload the whole data. i am just
asking if makes sense, not requesting to implement it.

>
>    mg> Since my website is already uploaded (it's a wordpress blog), I would
>    mg> find useful that the plug-in had a command to inform the remote copy
>    mg> about the latest revision uploaded, instead of forcing me to upload
>    mg> everything.
>
> We have to start somewhere. Once the first upload is done, the
> plugin upload an additional file (.bzr-upload.revid) which
> contains the corresponding revid. This revid can then be used to
> do incremental uploads.

will try a little hack with this



>
>    mg> But my point here, is that the documentation can lead to
>    mg> confusion since it does not talk about working trees and
>    mg> seems to imply that a bzr-info-less is uploaded.
>
> :-/
>
> Patches making things clearer are welcome.

here it goes (rewording needed), for the built-in help displayed with
bzr help upload :

i would change this :

============================
Description:
  If no destination is specified use the last one used.
  If no revision is specified upload the changes since the last upload.
============================

for this :

============================
Description:
  If no destination is specified use the last one used.
  If no revision is specified upload the changes since the last
upload. The first time it is used the whole working tree is uploaded,
even if -r is used.
============================