Github & Esp32 question

Community General Discussion
1

Hello everyone. Recently the ESP32 support package has updated from 3.0.7 to 3.1.0. I'd like to "git clone" the Espressif's IDF version which is used with this Arduino Core.

To be exact: how to clone Espressif ESP-IDF version "v5.3.2-174-g083aad99cf-dirty" ? I am not an experienced user of git (I am more cvs/svn guy :)) but brief look at branches there show no signs of any branch or tag "...-dirty". Or may be I do it wrong :-/.

Recent update broke my build and I want to see what did they change in that particualr version of IDF

Thanks!

2

Do you have a link?

3
4

Release 5.3.2:

5

The thing with Git is that after every set of changes, or commit, the content is hashed. It uses SHA -- forget which flavor -- so it's sometimes called that. You only need as many hex digits of the hash to be distinguishing; often only the first 7 or 8. Any commit can also be tagged: assigned a useful name, like a version number. You clone the entire repository, with all its commits and branches (up to that point in time -- it always has to be updated manually); then checkout a particular branch or commit.

GitHub uses an entirely reasonable URI-path scheme for releases.
The release page for 5.3.2 is github.com/espressif/esp-idf/releases/tag/v5.3.2 Note the hash listed there is 9d7f2d6; you can see what was done for that

$ git log --stat 9d7f2d6
commit 9d7f2d69f50d1288526d4f1027108e314e8c879f (tag: v5.3.2)
Author: Marius Vikhammer <marius.vikhammer@espressif.com>
Date:   Thu Dec 5 15:30:21 2024 +0800

    change(version): Update version to 5.3.2

 .gitlab/ci/common.yml                           | 2 +-
 components/esp_common/include/esp_idf_version.h | 2 +-
 tools/cmake/version.cmake                       | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

That first line with the commit also mentions any associated tag(s). The --stat option lists the changed files, and you can use the tag instead: git log v5.3.2

Note that is not the same hash as in v5.3.2-174-g083aad99cf-dirty. For one thing, g is not a valid hex digit. And the fact that it is -dirty implies it was a one-off build that is not in the official repository. However, on a hunch, if the g or 174-g means something, skipping it:

$ git log 083aad99cf
commit 083aad99cfc1a7981009ac7f18e29824c47ffba2
Merge: 9d3917d532 8bfabe711a
Author: Alexey Gerenkov <alexey@espressif.com>
Date:   Tue Dec 10 21:54:56 2024 +0800

That's five days later, and maybe as close as you can (easily) get.

$ git checkout 083aad99cf
1 Like
6

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.