git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Drew Northup <drew.northup@maine.edu>
To: Jim Vahl <jv@wmdb.com>
Cc: git@vger.kernel.org, "'Skot Davis'" <skotd122@gmail.com>
Subject: Re: A basic question
Date: Wed, 10 Oct 2012 15:36:34 -0400	[thread overview]
Message-ID: <1349897794.32696.15.camel@drew-northup.unet.maine.edu> (raw)
In-Reply-To: <001501cda711$8ab6f0a0$a024d1e0$@com>

On Wed, 2012-10-10 at 11:03 -0700, Jim Vahl wrote:
> All,
> 
> Our company is researching version control software, something which we have
> not used previously.  I have a very basic question about git which I have
> not been able to answer from reading.  As I understand it, a git repository
> can be a mixture of files which are under development, staged or committed.
> If we make a new build of our product we will obviously only want to include
> the committed (tested) files.  
> 
> The question is this: what is the usual procedure to retrieve a set of
> committed  files only from the repository to place into a distribution or
> "ready to build" folder.  The same question goes for tagging a release: how
> does the user get the tag to reference the committed files only and not the
> most recent files which may be under development or undergoing testing.
> 
> Thanks,
> 
> Jim Vahl

Jim,
Have you looked at http://git-scm.com/book yet? It sounds to me like you
have some misconceptions about how Git works. (If so, did it leave you
more or less confused?)

-- 
-Drew Northup
________________________________________________
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59

  reply	other threads:[~2012-10-10 19:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 18:03 A basic question Jim Vahl
2012-10-10 19:36 ` Drew Northup [this message]
2012-10-11 17:38   ` Jim Vahl
2012-10-11 18:40     ` James Nylen
     [not found]     ` <CA++fsGFruWFauX3XkynwcRLqK9H16frW86of3Y3ScgzGFmz=dg@mail.gmail.com>
2012-10-11 18:46       ` Dov Grobgeld
2012-10-12 15:56       ` A basic question - Thanks to all responders Jim Vahl
2012-10-11 18:51     ` A basic question Enrico Weigelt
2012-10-12  0:58     ` Sitaram Chamarty
2012-10-12  1:08     ` PJ Weisberg

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=1349897794.32696.15.camel@drew-northup.unet.maine.edu \
    --to=drew.northup@maine.edu \
    --cc=git@vger.kernel.org \
    --cc=jv@wmdb.com \
    --cc=skotd122@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).