what I was trying to say is: your repo contains the files inside
administrator folder, so you can make a new folder called administrator
inside your repo and move all the files in the repo inside that folder.
Then the folder that contains your repo can be renamed to appointments and
moved one level
legroups.com
Sent: Monday, July 20, 2015 4:39 PM
Subject: Re: [git-users] creating a new branch
Why move the repo one folder up...
It is already there...at C:\Apache24\htdocs\Appointments\Administrator\
I do not quite understand...but more importantly...changing the dir structure
of
Why move the repo one folder up...
It is already there...at C:\Apache24\htdocs\Appointments\Administrator\
I do not quite understand...but more importantly...*changing the dir
structure of my web project it is something I want to avoid..*..
Τη Δευτέρα, 20 Ιουλίου 2015 - 6:17:52 μ.μ. UTC+3, ο χρ
Assuming that those are the only folders (and files), one solution could
be: move all your files (git mv) inside a folder called
"Administrator" (like C:\Apache24\htdocs\
Appointments\Administrator\Administrator) and then move the repo one folder
up.
I think this will be the easiest solution, of
On Mon, Apr 21, 2014 at 4:35 PM, Konstantin Khomoutov
wrote:
> On Mon, 21 Apr 2014 05:53:41 -0700 (PDT)
> Simon Joseph Aquilina wrote:
>
>> Thanks for your reply. Reading your reply make me think that it is
>> common practice to delete branches after development on these has
>> finished (for exam
Take a look (if you did not yet) at this two articles:
1- http://scottchacon.com/2011/08/31/github-flow.html
2- http://nvie.com/posts/a-successful-git-branching-model/
2014-04-22 3:20 GMT-03:00 Gergely Polonkai :
> Another common practise for release naming is the usage of tags. In my
> project
Another common practise for release naming is the usage of tags. In my
projects, for example, I have several tags like v1.0.0, v2.4.2 and such.
On 21 Apr 2014 14:53, "Simon Joseph Aquilina"
wrote:
> Hi Konstantin,
>
> Thanks for your reply. Reading your reply make me think that it is common
> pra
On Mon, 21 Apr 2014 05:53:41 -0700 (PDT)
Simon Joseph Aquilina wrote:
> Thanks for your reply. Reading your reply make me think that it is
> common practice to delete branches after development on these has
> finished (for example branches used only to solve a bug or add a
> feature). Is this so.
Hi Konstantin,
Thanks for your reply. Reading your reply make me think that it is common
practice to delete branches after development on these has finished (for
example branches used only to solve a bug or add a feature). Is this so.
I was planning to also have branches for releases. For examp
On Mon, 21 Apr 2014 02:55:50 -0700 (PDT)
Simon Joseph Aquilina wrote:
> I am new to git and I would like to know what are the best practices
> when creating a new branch. For example. If I get a request to do
> update website title from XYZ to ABC; then should I create a branch
> named; "Update T
10 matches
Mail list logo