gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] migrating projects


From: Dustin Sallings
Subject: Re: [Gnu-arch-users] migrating projects
Date: Mon, 15 Sep 2003 10:05:53 -0700


On Monday, Sep 15, 2003, at 06:47 US/Pacific, Robert Collins wrote:

On Mon, 2003-09-15 at 17:31, Dustin Sallings wrote:

---------- First Problem ----------
        I've read of a patch that allows you to declare any file not
explicitly added should be ignored (i.e. CVS behavior).  Is this the
way to handle this in the future, or is there a better way?

{arch}/\=tagging-method is your friend. See the tutorial, and the
contents of that file. The patch in question is not appropriate for
solving the problem you have - and is (hopefully) already superceded by
a more general solution from Tom.

I was under the impression that there was a patch that would make arch ignore stuff that wasn't explicitly added. This seems desirable, as I like to leave junk around in build trees when I'm doing stuff (disposable test scripts, output, sample input, etc...).

        Is there a ``subcategory'' concept?  I'd like to create a ``lang''
category that contains a subcategory for each language I have various
toys written in.  Recursive would be grand, as I've got things like
c/net/tcp/{project}.

I'd probably consider the language to be orthogonal to the project at
hand, so perhaps:
toys--net-tcp--1.0 ?

That's kind of interesting. It seems a little abusive to the branch concept, but it could work.

I realize it sounds a strange that I'm considering a language a category, but a lot of what I end up with is either sample code or little tiny apps that are too small to be their own projects, and I like to keep those categorized.

--
Dustin Sallings





reply via email to

[Prev in Thread] Current Thread [Next in Thread]