Okay, newbie question. Organization Foo has developers Sam, Fred, and
Guido. The org clones Project X and over time realizes their own branch
needs to be separate from the project for a while. Sam, Fred, and Guido
each branch their code for the parts of the project they are working on.
When
I'm trying to design a workflow for our team and could use some advice. My
git-fu is young.
We have a remote repo that will store the authoritative code. That will be
pulled to a server local repo where the team has access. Each person will
clone the local repo into their home directory,
Hey all, I'm still learning.
Is there a HOWTO or tutorial for how to control owner, group, and
permissions on files as they get checked in? The ideal is that the owner
and group change to X and Y and the permissions are set to 770. I'd
like to figure out how to do and test that.
Thoughts?
On Tuesday, December 9, 2014 1:32:28 PM UTC-5, leam hall wrote:
Hey all, I'm still learning.
Is there a HOWTO or tutorial for how to control owner, group, and
permissions on files as they get checked in? The ideal is that the owner
and group change to X and Y and the permissions are set
Working on a project that's importing code from an older project. There are
2-3 dozen small bits and we're trying to add some functionality and clean
up the code in each small bit. Would it make sense to make each small bit
it's own branch? The theory is that as each branch becomes workable it
On Thu, Aug 13, 2015 at 4:11 AM, Martin Møller Skarbiniks Pedersen
traxpla...@gmail.com wrote:
On 12 August 2015 at 16:05, leam hall leamh...@gmail.com wrote:
On Wednesday, August 12, 2015 at 12:52:24 AM UTC-4, GadgetSteve wrote:
On 11/08/2015 15:41, leam hall wrote:
Is there a way
Is there a way to suppress the normal ssh banner when doing a git pull?
Something equivalent to ssh -q? If I missed a README, please point me in
that direction.
Thanks!
Leam
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To
On Wednesday, August 12, 2015 at 12:52:24 AM UTC-4, GadgetSteve wrote:
On 11/08/2015 15:41, leam hall wrote:
Is there a way to suppress the normal ssh banner when doing a git pull?
Something equivalent to ssh -q? If I missed a README, please point me
in that direction.
Thanks
Hey y'all,
I'm not complaining about the magic, but would like to understand. If user
C is coding on a git branch and user R goes into that code's directory,
then R will see whatever files are in the current branch. If C changes
branches, R's view will also change. How does that happen?
Also, a free on-line book: https://git-scm.com/book/en/v2
On 02/10/16 18:37, Suu wrote:
Before I build/compile a git branch, I would like to know whether it has
changed since the last time I built it.
If no change, I won't bother to build.
in Subversion, it's a "revision number" that
)
-Original Message-
From: Leam Hall [mailto:leamh...@gmail.com]
Sent: Wednesday, February 10, 2016 3:35 PM
To: git-users@googlegroups.com
Subject: Re: [git-users] Building GIT: how to get the set of source code
on a branch in order to build it?
Case 1:
git clone
Case 2:
cd
Hmm...depends. Yes, the git hash will be the same if you're on the same
version. How manual do you want it to be? "git status" will show you the
status but isn't manual.
You can "git log | head -1' for the commit hash, if that's what you
want. For example:
git log | head -1
Project A has config files and other stuff. Project B is a superset of
Project A, it includes everything in A plus more. We often need to update a
file in A and deploy the new stuff. However, any server that currently gets
A should get nothing of B. However, a server getting the updated B files
Hopefully I can explain this well...
We have some files that are generated as a part of the build process. So
they can get updated frequently during some coding events. They must be in
the repo since other tools use these specific files, but do not run the
build process. However, if there is a
, Aug 19, 2020 at 10:00 PM Leam Hall wrote:
Hopefully I can explain this well...
We have some files that are generated as a part of the build process. So
they can get updated frequently during some coding events. They must be in
the repo since other tools use these specific files, but do not r
Before I go off and make changes, can you help me understand this warning?
I get the concept, but haven't seen this one before.
warning: inexact rename detection was skipped due to too many files.
warning: you may want to set your merge.renamelimit variable to at least
1232 and retry the
16 matches
Mail list logo
