[pjb@kuiper :0 patchwork]$ fossil push
Server:http://fossil.informatimago.com:8002/patchwork
Bytes Cards Artifacts Deltas
Sent: 268 4 0 0
Error: not authorized to write
Received: 65 1 0 0
On Mon, May 07, 2012 at 06:23:53PM +0200, Pascal J. Bourguignon wrote:
What's wrong? What should I do to push my commits?
Your answer is in the output of your failed fossil push:
Error: not authorized to write
--
James Turner
ja...@calminferno.net
James Turner ja...@calminferno.net writes:
On Mon, May 07, 2012 at 06:23:53PM +0200, Pascal J. Bourguignon wrote:
What's wrong? What should I do to push my commits?
Your answer is in the output of your failed fossil push:
Error: not authorized to write
Why am I not?
I created the remote
On Mon, May 7, 2012 at 7:02 PM, Pascal J. Bourguignon p...@informatimago.com
wrote:
I re-cloned the local from the remote.
When you cloned it, did you add username:password to the URL? If not, try
cloning with that. It doesn't look like you did because the Server: line
does not show your
I think this is a good illustration of how noisy output makes it hard for
new users to see problems occurring. I would prefer to see most of the sync
output suppressed unless a verbose switch is flipped. Most of the time
people really only need to know that the sync succeeded or failed. At the
Stephan Beal sgb...@googlemail.com writes:
On Mon, May 7, 2012 at 7:02 PM, Pascal J. Bourguignon
p...@informatimago.com wrote:
I re-cloned the local from the remote.
When you cloned it, did you add username:password to the URL? If not,
try cloning with that. It doesn't look like you
Matt Welland estifo...@gmail.com writes:
I think this is a good illustration of how noisy output makes it hard
for new users to see problems occurring. I would prefer to see most of
the sync output suppressed unless a verbose switch is flipped. Most
of the time people really only need to
7 matches
Mail list logo
