* Joe Buck:
> Well, maybe. But what about a revision that modifies code and that
> also modifies the WWW to describe the code modification? If everything
> were in the same subversion repository, it could be one change.
Only if you check out a common parent directory, which is probably not
a co
On Mon, Oct 31, 2005 at 05:31:51PM +0100, Gerald Pfeifer wrote:
> Per se there doesn't seem to be as much of an advantage for wwwdocs
> as we had for gcc (no branches, most changes only to one or two files,
> no need for binary regression search, no tagging,...) so it's not
> urgent.
Well, maybe.
On Mon, 31 Oct 2005, Gerald Pfeifer wrote:
> On Sun, 16 Oct 2005, Daniel Berlin wrote:
> > I should probably note again that i don't plan to convert wwwdocs to svn
> > right now, because the checkout scripts are a bit hard to follow, etc.
>
> Per se there doesn't seem to be as much of an advant
On Sun, 16 Oct 2005, Daniel Berlin wrote:
> I should probably note again that i don't plan to convert wwwdocs to svn
> right now, because the checkout scripts are a bit hard to follow, etc.
Per se there doesn't seem to be as much of an advantage for wwwdocs
as we had for gcc (no branches, most c
On Fri, 2005-10-14 at 11:40 +, Joseph S. Myers wrote:
> On Fri, 14 Oct 2005, Kaveh R. Ghazi wrote:
>
> > their corresponding svn commands posted on the website? Hmm, I guess
> > we would need to update these pages to the svn equivalents which would
> > pretty much cover the basics of a how-to
(Sorry for the C-n-P, my regular email is down till sunday afternoon.
Hopefully notes won't screw this email up too badly)
>Has any thought been put into helping the 200+ people with write
>access migrate?
Of course
There is a basic how to guide for CVS users on the wiki, at
http://gcc.gnu.or
On Fri, 14 Oct 2005, Kaveh R. Ghazi wrote:
> their corresponding svn commands posted on the website? Hmm, I guess
> we would need to update these pages to the svn equivalents which would
> pretty much cover the basics of a how-to guide:
>
> http://gcc.gnu.org/cvs.html
> http://gcc.gnu.org/cvswri
> I'm actually in the middle of building a fully merged + converted repo
> (IE exactyl what the final repo will look like, including the merge
> from old-gcc).
>
> It should be done in another 10 hours or less.
>
> I was planning to announce it and update the wiki's page so that those
> w
On Thu, 2005-10-13 at 15:54 -0700, Mike Stump wrote:
> On Oct 8, 2005, at 5:47 PM, Daniel Berlin wrote:
> > Thus, i'm going to put an updated repo on gcc.gnu.org on Monday (i was
> > converting it
>
> Could I request that:
>
> svn ls svn+ssh://gcc.gnu.org/export/u0/gccsvn/gccrepo/branches | grep
On Oct 8, 2005, at 5:47 PM, Daniel Berlin wrote:
Thus, i'm going to put an updated repo on gcc.gnu.org on Monday (i was
converting it
Could I request that:
svn ls svn+ssh://gcc.gnu.org/export/u0/gccsvn/gccrepo/branches | grep
-i apple
output a line or two (or five) before in a test repo be
On Tue, 2005-10-11 at 02:02 +0200, Giovanni Bajo wrote:
> Daniel Berlin <[EMAIL PROTECTED]> wrote:
>
> > Thus, i'm going to put an updated repo on gcc.gnu.org on Monday (i was
> > converting it, but it looks like they shutdown the machines at watson)
> > and do a few test branch merges to make sur
Daniel Berlin <[EMAIL PROTECTED]> wrote:
> Thus, i'm going to put an updated repo on gcc.gnu.org on Monday (i was
> converting it, but it looks like they shutdown the machines at watson)
> and do a few test branch merges to make sur eall the commit mails come
> out okay for very large cases.
Will
On Sat, Oct 08, 2005 at 08:47:19PM -0400, Daniel Berlin wrote:
>Angela, you said you had a good solution to the restricted shell problem
>(IE the need to allow both cvs server and svnserve to run).
? I wrote a script which seems to work for providing a restricted shell.
Does Angela have something
Okay, well, i've got the svn mailer config setup okay, and tested to
make sure it posts the right messages to the right mailing lists for the
right dirs
ViewCVS is now up on an old test repo at http://gcc.gnu.org/viewcvs and
working okay.
Thus, i'm going to put an updated repo on gcc.gnu.org on
14 matches
Mail list logo