[mylvmbackup] Re: a2x?

Hi Matthew,

On 09/24/2008 07:20 PM, Boehm, Matthew wrote:

> I read up on perl POD formatting. Seems simple enough. So I converted the
> existing man txt source to a POD. The built-in utilities pod2man, pod2txt and
> pod2html seem to fit the requirement of being able to make different formats.

Indeed, thanks for looking into this!

> I've altered the makefile accordingly and added the POD file. But now I
> have bzr issues. I'm a brand new user so please bear with me.

No problem. bzr take a while to get used to it, but once you've mastered it,
you don't want to miss it :)

> This is throwing me for a loop:
> 
> [root@15000Dmys01 mylvmbackup]# bzr up
> Tree is up to date at revision 78.
> 
> Wtf? Launchpad says current rev is 80. Why won't bzr update? I did a fresh
> checkout this morning, so also, why did it check out 78 instead of 79 to begin
> with?

Interesting, indeed. Did you commit a revision before you ran "bzr pull"? Does
the revision history ("bzr log") match? Note that revision numbers are not
stable across trees. They are just an aid to easily work with revisions within
a local repository. Each revision also has a unique revision ID, that you can
display by using "bzr log --show-ids". This ID does not change when merging
revisions from one tree into another.

> What's the proper procedure for submitting changes like this? Do you want 1
> patchfile? Or is there something I should do with bzr?

The proper way of doing this would be to create branch off the main repository
on Launchpad. Then you make your changes and publish your branch on Launchpad
using "bzr push". That makes it easy for me to merge your changes into the
main branch.

Bye,
        LenZ
-- 
------------------------------------------------------------------
 Lenz Grimmer <lenz@xxxxxxxxxxx>                             -o)
 [ICQ: 160767607 | Jabber: LenZGr@xxxxxxxxxx]                /\\
 http://www.lenzg.org/                                       V_V

Other related posts: