Closed GoogleCodeExporter closed 9 years ago
(I thought I could edit my initial post to add the link to the files I
mentionned, but I'll post it as a comment here instead)
https://github.com/pixelastic/sov/tree/master/issues/boar/84
Original comment by timcc.pe...@gmail.com
on 25 Oct 2012 at 5:18
Confirmed. This is an obvious bug. Using the "setprop" command with the "-f"
will always give this error in the boar.29-Jul-2012 release.
Original comment by ekb...@gmail.com
on 25 Oct 2012 at 7:34
I cloned the mercurial repo (commit 5db5e7bc60ab) and the issue is also
present. I'll keep an eye on future commits. Thanks.
Original comment by timcc.pe...@gmail.com
on 25 Oct 2012 at 9:18
This issue was closed by revision 2f40f2503283.
Original comment by ekb...@gmail.com
on 25 Oct 2012 at 8:03
Thanks, this fixed the issue.
But I still need to include to `--repo` option, even if I'm in a dir that is
already tracked by boar. I mean I can issue `boar status` just fine, but I need
to add the `--repo` option for `boar setprop`.
Is that the intended behavior ?
Original comment by timcc.pe...@gmail.com
on 26 Oct 2012 at 8:30
Yes, that is actually the intended behaviour. Since the command can have
serious consequences if you apply it to the wrong session, it intentionally
doesn't use the workdir session by default. You can compare that to the
"ls" command that can be used with or without a workdir, but that command
has no side effects if you accidentially execute it in the wrong place.
However, it would be convenient and just as safe to add a flag to apply
the setprop to the workdir session. Alas, there are many similar simple
enhancements that would make Boar a little bit easier to use and should be
implemented at some time. I add a few every now and then, and I'll keep
this one in mind.
Original comment by ekb...@gmail.com
on 26 Oct 2012 at 8:44
Ok, that makes sense. I'm still a bit confused about the "repo" term but I
guess a bit more practice of boar is all I need to get it.
Thanks.
Original comment by timcc.pe...@gmail.com
on 27 Oct 2012 at 9:07
Original issue reported on code.google.com by
timcc.pe...@gmail.com
on 25 Oct 2012 at 5:13