11:33 p.m.
Updating -gretl- has gone well, so far. But is this normal?
clive@clivubu:~/gretl-git$ sudo git config --global push.default simple
clive@clivubu:~/gretl-git$ sudo git pull
Already up-to-date.
clive@clivubu:~/gretl-git$ sudo git commit -a
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
Makefile
build.h
builddate
cli/.deps/
cli/.libs/
cli/Makefile
cli/complete.o
cli/debug
cli/gretlcli
cli/gretlcli.o
config.h
config.log
config.status
doc/Makefile
doc/commands/.libs/
doc/commands/Makefile
doc/commands/bbl2txt
doc/commands/cmdtex
[...]
tests/Makefile
utils/emacs/Makefile
xdg/Makefile
xdg/gretl.desktop
nothing added to commit but untracked files present
clive@clivubu:~/gretl-git$ sudo git push
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
That's not happened before and this is a clean gretl-git folder from Sunday
night. Thoughts?
--
Clive Nicholas
"My colleagues in the social sciences talk a great deal about methodology.
I prefer to call it style." -- Freeman J. Dyson
12:08 a.m.
Hi,
(we should move this discussion to the gretl-devel mailing list)
clive@clivubu:~/gretl-git$ sudo git push
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
You really like to sudo git ;)
(no need for sudoing git!)
If I got right you wanted to push changes (none) to the "simple"
repository, so you set it as default.
But probably your repository is "origin". You may check what repositories
you have with:
git remote -v
To know what branches you do:
git branch -a
When I want to push my changes I do:
# before I selected the branch I am working at, for example "master", with
"git checkout master"
git add -i
# interactively select what files to push
git commit
# actually put them on the queue to push
git push origin master
# select the repository and branch and upload changes
That's not happened before and this is a clean gretl-git folder
from
Sunday night. Thoughts?
The files you have on your disk are new files (and they ARE NOT to be
pushed). It
happens the same in my system.
This git stuff is a new thing in this project and we must set the
.gitignore file with the extensions and directories to be ignored (either
on our own systems and on github/sourceforge).
1:05 a.m.
On Mon, 26 Oct 2015, Clive Nicholas wrote:
Updating -gretl- has gone well, so far. But is this normal?
clive@clivubu:~/gretl-git$ sudo git config --global push.default simple
clive@clivubu:~/gretl-git$ sudo git pull
Well, "sudo" is not normal in this context!
Already up-to-date.
clive@clivubu:~/gretl-git$ sudo git commit -a
Clive, what are you trying to commit? Have you made any changes to
the sources?
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
Makefile
build.h
These "untracked" files (and there will be _many_ of them) were
generated in the course of your build. They are not primary source
files and don't belong in the git repository.
nothing added to commit but untracked files present
clive@clivubu:~/gretl-git$ sudo git push
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
You don't have write permission on the sourceforge gretl-git
repository; and moreover you don't have anything to commit/push.
That's relevant only if you are a developer with new code or
revisions to make available.
As someone just building gretl from git to be bang up-to-date, the
only git command you'll need is "git pull" from time to time, to
update your local copy of the sources.
The cleanest way to keep the generated files separate from the ones
under version control (i.e. that belong in git) is to build "out of
tree". Instead of doing ./configure and make inside gretl-git, you
can create a parallel directory -- say, gretl-build: cd into that
and (assuming the two directories are at the same hierarchical
level), do
../gretl-git/configure <your options>
make
[etc.]
That way the git sources will remain pristine. Alternatively, to the
same effect, you can create your build directory inside the
gretl-git directory, as in:
cd gretl-git
mkdir build
cd build
../configure <your options>
make
[etc.]
In the second case you can create a text file ~/.config/git/ignore
with content:
build/
and git will ignore the contents of your build directory rather than
reporting them as "untracked".
Meanwhile, "make clean" will get rid of many of the generated files
in the git tree itself. ("make distclean" ought to do a more
comprehensive job, but I see it's not working properly; that's
something we need to fix.)
Allin
3:31 a.m.
Allin,
I'm still studying this. I'll get back to you once I've fully digested and
thought through its contents.
C
On 27 October 2015 at 01:05, Allin Cottrell <cottrell(a)wfu.edu> wrote:
On Mon, 26 Oct 2015, Clive Nicholas wrote:
Updating -gretl- has gone well, so far. But is this normal?
>
> clive@clivubu:~/gretl-git$ sudo git config --global push.default simple
> clive@clivubu:~/gretl-git$ sudo git pull
>
Well, "sudo" is not normal in this context!
Already up-to-date.
> clive@clivubu:~/gretl-git$ sudo git commit -a
>
Clive, what are you trying to commit? Have you made any changes to the
sources?
On branch master
> Your branch is up-to-date with 'origin/master'.
> Untracked files:
> Makefile
> build.h
>
These "untracked" files (and there will be _many_ of them) were generated
in the course of your build. They are not primary source files and don't
belong in the git repository.
nothing added to commit but untracked files present
> clive@clivubu:~/gretl-git$ sudo git push
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
You don't have write permission on the sourceforge gretl-git repository;
and moreover you don't have anything to commit/push. That's relevant only
if you are a developer with new code or revisions to make available.
As someone just building gretl from git to be bang up-to-date, the only
git command you'll need is "git pull" from time to time, to update your
local copy of the sources.
The cleanest way to keep the generated files separate from the ones under
version control (i.e. that belong in git) is to build "out of tree".
Instead of doing ./configure and make inside gretl-git, you can create a
parallel directory -- say, gretl-build: cd into that and (assuming the two
directories are at the same hierarchical level), do
../gretl-git/configure <your options>
make
[etc.]
That way the git sources will remain pristine. Alternatively, to the same
effect, you can create your build directory inside the gretl-git directory,
as in:
cd gretl-git
mkdir build
cd build
../configure <your options>
make
[etc.]
In the second case you can create a text file ~/.config/git/ignore
with content:
build/
and git will ignore the contents of your build directory rather than
reporting them as "untracked".
Meanwhile, "make clean" will get rid of many of the generated files
in the git tree itself. ("make distclean" ought to do a more comprehensive
job, but I see it's not working properly; that's something we need to fix.)
Allin
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users
--
Clive Nicholas
"My colleagues in the social sciences talk a great deal about methodology.
I prefer to call it style." -- Freeman J. Dyson
3351
days inactive
3353
days old
3 comments
3 participants
participants (3)
-
Allin Cottrell -
Clive Nicholas -
Hélio Guilherme