Yep. All good. Thanks for checking.
--sent from my Samsung Galaxy S III phone
On Mar 30, 2013 4:30 AM, "Patrick Dickey" wrote:
> Hi Jim,
>
> Were you able to push your commits now? If not, just try bzr push and it
> will guide you from there. What I typically use (because it came up when I
> did
Hi Jim,
Were you able to push your commits now? If not, just try bzr push and it
will guide you from there. What I typically use (because it came up when I
did bzr push) is bzr push :parent
Have a great weekend. :)
Patrick.
On Fri, Mar 29, 2013 at 10:47 AM, Jim Connett wrote:
> Thanks, Kevin.
Thanks, Kevin...that worked!
On Thu, Mar 28, 2013 at 6:52 PM, Kevin Godby wrote:
> Hello, Jim.
>
> On Thu, Mar 28, 2013 at 7:54 PM, Jim Connett
> wrote:
> > Thanks, Mike, for the quick reply...just ran it at the command line and
> > here's what I got:
> >
> > bzr: ERROR: Cannot lock
> > LockDi
Hello, Jim.
On Thu, Mar 28, 2013 at 7:54 PM, Jim Connett wrote:
> Thanks, Mike, for the quick reply...just ran it at the command line and
> here's what I got:
>
> bzr: ERROR: Cannot lock
> LockDir(http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/raring/.bzr/branch/lock):
> Transport opera
No worries. Thanks for your input.
On Thu, Mar 28, 2013 at 6:10 PM, Mike Romard wrote:
> Unfortunately I'm not sure what to suggest at this point. I hope someone
> with more bazaar experience can point you in the right direction.
>
> Mike
>
>
>
> On 28 March 2013 21:54, Jim Connett wrote:
>
>>
Unfortunately I'm not sure what to suggest at this point. I hope someone
with more bazaar experience can point you in the right direction.
Mike
On 28 March 2013 21:54, Jim Connett wrote:
> Thanks, Mike, for the quick reply...just ran it at the command line and
> here's what I got:
>
> bzr: ERR
Thanks, Mike, for the quick reply...just ran it at the command line and
here's what I got:
bzr: ERROR: Cannot lock LockDir(
http://bazaar.launchpad.net/~ubuntu-manual/ubuntu-manual/raring/.bzr/branch/lock):
Transport operation not possible: http does not support mkdir()
On Thu, Mar 28, 2013 at
Hi, Jim. The command that I used to make my changes was:
bzr push lp:ubuntu-manual
I think you just need to leave off the "/raring".
I've run into a launchpad ID error before as well. If I recall correctly, I
got around it by repeating step 2 in "Creating a Launchpad Account" here:
http://ubun
Did my first edits on this manual. I've committed the changes to make
revision 86. But I can't push the changes. Here's my command:
bzr push lp:ubuntu-manual/raring
I think I have the path incorrect. I tried to deduce it from the feedback I
got back in the error message, but I must be incorrect.
I think I tried Bazaar Explorer once or twice a while back. And I've
tried Ground Control (when it was being developed at least). One thing
that we should make clear is, if you're using a GUI and are having
problems, let us know that. All of the steps that I gave Mehmet earlier
were command line st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Am 23.03.2013 06:45, schrieb Kevin Godby:
> I've had some questions recently about how to use bzr.
Thanks for this nice explanation. I only want to mention that there
are some GUIs for bzr available. For Example I use »Bazaar Explorer«.
Greeting
Hello, everyone.
I've had some questions recently about how to use bzr. Here's a link
to some instructions that I wrote some time ago. It seems like a good
time to post it again.
https://docs.google.com/document/d/1LDAyOVGMOLvsMTef3dTE3zt9q-gQY_-NetMKfZ6yM2Q/edit?usp=sharing&authkey=CLynx-cH
If
I created a script to automate this process. I recommend that this be
included in the branch as to make it easier and to prevent mistakes. Here is
the script:
#!/bin/bash
#Copyright (c) 2010, Jason Cook
#All rights reserved.
> #Redistribution and use in source and binary forms, with or without
better yet, use bzr commit --fixed=lp: -m
> wrote:
> Hi Jason,
>
> Yes you can fix multiple bugs and then commit/push, rather than doing so
> after each bug. The commit operation will record any changes you have made
> across the whole ubuntu-manual branch. Just make sure you list the bug
> numbe
Hi Jason,
Yes you can fix multiple bugs and then commit/push, rather than doing so
after each bug. The commit operation will record any changes you have made
across the whole ubuntu-manual branch. Just make sure you list the bug
numbers you have addressed in the [comment] when you run bzr commit -
You can fix multiple bugs and then commit and push, yes. Just make sure you
include a commit phrase that has the bug numbers you've fixed, for example:
"Fixed bugs 50481, 28105, 50856"
On Wed, May 26, 2010 at 1:04 PM, Jason Cook wrote:
> Thanks for this guide. I have just started fixing bugs to
Thanks for this guide. I have just started fixing bugs today and I have a
few questions. Each time you change a bug do you need to "commit and push"
or can you change multiple bugs and then "commit and push".
The command to run are when you make a change are:
cd ~/Projects/ubuntu-manual
make clean;
Hello, all.
I wanted to thank everyone who's helped so far with reporting and
fixing bugs in the manual. We really appreciate it!
Unfortunately, we've had a few new bugs slip in to the code in the
process. So here's a quick guide on how to commit code for our
manual:
1. We're commit our code a
18 matches
Mail list logo
