On Fri, Jan 17, 2014 at 6:16 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote:
> On Fri, 17 Jan 2014 17:59:42 +0200 > Nikos Balkanas <nbalka...@gmail.com> wrote: > > [...] > > > OK, so you have been told to check out a revision by the SHA-1 name > > > of its commit, and so you did. > > > > > > Also please answer the most important question: why do you think > > > something's wrong with your checkout? > > > And can we please see the result of `git status`? I'm asking this > > > because this might shed some light on the issue -- say, it'll list > > > many modified or missing or untracked files. > [...] > > # aclocal.m4 > > # autom4te.cache/ > > # config.h.in > > # config.log > > # config.status > > # config/Makefile.in > > # configure > > # depcomp > > # gnuradio-core/Makefile > > # gnuradio-core/Makefile.in > [...] > > I see already part of the problem. I wasn't told to check out any > > version in particular. I just need a specific version to work > > together with my other programs. The revision # i got from the > > repository and it is good. Apparently they didn't do a very good job > > of tracking files :-( I will add these and see what i have. > > Wait! All these files seem to be generated by autoconf and/or > by running ./configure. They *might* not be supposed to be tracked > (at least **/Makefile -- for sure). I would ask the fellow developers > about these matters. > > Having said that, I'm oblidged to ask again: with the information > you've gained during our exchange, what's wrong with your checkout? > I mean, I suspect we're dealing with an "XY problem" [1]. > > My impression is that it didn't work, since the first checkout returned immediately and i didn't notice any file or dir differences. Mind you, I am trying to get to version 2.8 of gnuradio, and I don't know which revision is that. I go by date. Repository is ~7 years back. Since then I have observed an extra dir, "gnuradio-core" that has been removed from the ditribution a few years back. At the moment it won't build. But this could be a bug in this particular release. I am trying to verify version by other means "grep -rn "version*"" etc. Don't worry, I thought about the same. and just added 1 track only. I will try to remove it. I will be able to be more specific once I fish out the version. I may be good ;-) > > > P.S. > > > Please don't top-post -- this breaks the discussion flow, which > > > sucks. > > Sorry about that, it is a gmail feature. I can respond in line, but > > gmail doesn't make it easy :-( > > Well, I just subscribe to the groups I want to participate in and use a > sensible MUA to reply to mails coming from them. > > But never mind, if it's hard to reply in line, do whatever works. > > 1. http://meta.stackoverflow.com/a/66378 > Nope it is not that big a deal. Just sometimes i forget to do it ;-) -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
