From owner-freebsd-current Sun Jun 20 23:53:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id 1AAE414C13 for ; Sun, 20 Jun 1999 23:53:26 -0700 (PDT) (envelope-from Kurt@OpenLDAP.Org) Received: from OpenLDAP.Org (localhost [127.0.0.1]) by cantor.boolean.net (8.9.2/8.9.1) with ESMTP id GAA67750; Mon, 21 Jun 1999 06:54:34 GMT (envelope-from Kurt@OpenLDAP.Org) Message-ID: <376DDFC3.2ADEF3F0@OpenLDAP.Org> Date: Sun, 20 Jun 1999 23:46:27 -0700 From: "Kurt D. Zeilenga" Organization: OpenLDAP X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en-GB,en-US,en,de-DE,de MIME-Version: 1.0 To: Chuck Robey Cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG, "Jordan K. Hubbard" , Alfred Perlstein Subject: Re: laying down tags References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > On Sun, 20 Jun 1999, Kurt D. Zeilenga wrote: > > > Tags can span time, span branches, and subsets of the repository. > > A tag may not represent a bulk commit. Tags are associated with > > specific revisions of files, not some arbitary date. > > Well, reading over this, it appears (though it's not clear) that you > agree that dates can do the job of tags. No, I said that under very limited circumstances, data specifiers can do the job of tags. The circumstances are quite limiting and require significant attention to details [ie: scouring of logs for the right date (and tag if commit was on a branch) to use]. If you want to cut down on space used by a tag, only tag subtrees. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message