On Wed, Dec 21, 2011 at 13:21, Stefan Sperling wrote:
> On Wed, Dec 21, 2011 at 06:07:05AM -0600, Ryan Schmidt wrote:
>> On Dec 20, 2011, at 06:08, Mojca Miklavec wrote:
>> > Is there any way to prevent
>> > deleting existing contents within the scope of command line arguments?
>> > A workaround is
On Wed, Dec 21, 2011 at 06:07:05AM -0600, Ryan Schmidt wrote:
> On Dec 20, 2011, at 06:08, Mojca Miklavec wrote:
> > Is there any way to prevent
> > deleting existing contents within the scope of command line arguments?
> > A workaround is to use something like
> >if [ ! -d "project" ]; then
>
On Dec 20, 2011, at 06:08, Mojca Miklavec wrote:
> I'm writing a script (also used as a cron job on the server) that
> should work independent of whether or not a checkout has already been
> done or not. I would like to do "repeated sparse checkout" as
> explained below, but I'm not sure how to do
Hello,
I'm writing a script (also used as a cron job on the server) that
should work independent of whether or not a checkout has already been
done or not. I would like to do "repeated sparse checkout" as
explained below, but I'm not sure how to do it properly. (I have some
kind of a workaround fo
