All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: Murray Jensen <Murray.Jensen@cmst.csiro.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc_2_4_devel rsync access
Date: Wed, 16 May 2001 01:27:00 -0600	[thread overview]
Message-ID: <20010516012700.G15908@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <25691.989985623@msa.cmst.csiro.au>; from Murray.Jensen@cmst.csiro.au on Wed, May 16, 2001 at 02:00:23PM +1000


The rsync tree is updated once per date (time is listed on the web page)
and it hasn't been updated today yet.

} Hi All, it appears that the linuxppc_2_4_devel rsync tree is not being
} updated from the bk tree. I have diffed the two and there are a lot of
} changes in the bk tree that don't appear in the rsync tree. Could someone
} check if the update is happening please? Thanks in advance. Cheers!
} 								Murray...
}
} PS: if you're wondering why I don't just use the bk tree, I like using the
} rsync tree because I import the sources into a local CVS repository and I
} don't have to worry about doing a bk get, and then ignoring bk control files
} and SCCS directories etc. (I will do this now, but the rsync is easier for
} me - if it is up to date).
} --
} Murray Jensen, CSIRO Manufacturing Sci & Tech,         Phone: +61 3 9662 7763
} Locked Bag No. 9, Preston, Vic, 3072, Australia.         Fax: +61 3 9662 7853
} Internet: Murray.Jensen@cmst.csiro.au  (old address was mjj@mlb.dmt.csiro.au)
}
}

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2001-05-16  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16  4:00 linuxppc_2_4_devel rsync access Murray Jensen
2001-05-16  5:05 ` Murray Jensen
2001-05-16  7:27 ` Cort Dougan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010516012700.G15908@ftsoj.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=Murray.Jensen@cmst.csiro.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.